Skip to content

Fix default values of PostbackScriptOptions#1926

Merged
tomasherceg merged 1 commit intomainfrom
postbackscriptoptions-default-values
May 30, 2025
Merged

Fix default values of PostbackScriptOptions#1926
tomasherceg merged 1 commit intomainfrom
postbackscriptoptions-default-values

Conversation

@exyi
Copy link
Copy Markdown
Member

@exyi exyi commented Apr 26, 2025

Resolves #1908

We now store all options as nullable, and the default value is determined by the KnockoutHelper function called. It is necessary, as GenerateClientPostbackLambda has a different set of default values than GenerateClientPostbackLambda, and GenerateClientPostbackScript.

Notable exception is the ReturnValue, which already is nullable and null means that null should be returned. It's thus technically difficult to make this property "optional", and this issue isn't really relevant for this property anyway

Resolves #1908

We now store all options as nullable, and the default value is determined by the KnockoutHelper function called.
It is necessary, as GenerateClientPostbackLambda has a different set of default values than GenerateClientPostbackLambda, and GenerateClientPostbackScript.

Notable exception is the ReturnValue, which already is nullable and null means that `null` should be returned.
It's thus technically difficult to make this property "optional", and this issue isn't really relevant for this property anyway
@tomasherceg tomasherceg merged commit 8e4b4fe into main May 30, 2025
14 of 16 checks passed
@tomasherceg tomasherceg deleted the postbackscriptoptions-default-values branch May 30, 2025 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GenerateClientPostbackLambda PostBackOptions inconsistency

2 participants